Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cc1abb6fed230f2abb14b5c27665db15d30c07fb88fb4bc6c229d6c6d998b52a

Tx prefix hash: 04836d7aec33f497d64635e10e086b7db9d6e2f9e2d97cb239f11ee7553e03e5
Tx public key: 2c1e7172a74df134567b87d2a64c165766fc3c9613275ed88bcdf4c95949d340
Timestamp: 1723709773 Timestamp [UCT]: 2024-08-15 08:16:13 Age [y:d:h:m:s]: 00:229:18:51:32
Block: 1088320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164079 RingCT/type: yes/0
Extra: 012c1e7172a74df134567b87d2a64c165766fc3c9613275ed88bcdf4c95949d340021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574d02d91e8e13baed89df122b1deb46998eb80ea7b0f894a9c94d984ccf62fb 0.600000000000 1562935 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1088330, "vin": [ { "gen": { "height": 1088320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574d02d91e8e13baed89df122b1deb46998eb80ea7b0f894a9c94d984ccf62fb" } } ], "extra": [ 1, 44, 30, 113, 114, 167, 77, 241, 52, 86, 123, 135, 210, 166, 76, 22, 87, 102, 252, 60, 150, 19, 39, 94, 216, 139, 205, 244, 201, 89, 73, 211, 64, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8