Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21f1f2362a2f0a52d1a2983202ad3f920657e9e80229cd9067dbb5f376ae05dd

Tx prefix hash: cd43ccf28423b9fb65445203fd28bc78947b86e89540502e0037d874391c7a05
Tx public key: 375a10317d8eba2d4eed3b733da03b1fd6ead091197320a2010c0c179995c662
Timestamp: 1578160429 Timestamp [UCT]: 2020-01-04 17:53:49 Age [y:d:h:m:s]: 04:327:18:25:31
Block: 38699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123413 RingCT/type: yes/0
Extra: 01375a10317d8eba2d4eed3b733da03b1fd6ead091197320a2010c0c179995c66202110000000fd81c26c0000000000000000000

1 output(s) for total of 456.851439653000 dcy

stealth address amount amount idx
00: 3e2230989a8fd0e308348501ad211bcbfc1aac3e1723efdeb97844b0b71a30b4 456.851439653000 66171 of 0

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": 38709, "vin": [ { "gen": { "height": 38699 } } ], "vout": [ { "amount": 456851439653, "target": { "key": "3e2230989a8fd0e308348501ad211bcbfc1aac3e1723efdeb97844b0b71a30b4" } } ], "extra": [ 1, 55, 90, 16, 49, 125, 142, 186, 45, 78, 237, 59, 115, 61, 160, 59, 31, 214, 234, 208, 145, 25, 115, 32, 162, 1, 12, 12, 23, 153, 149, 198, 98, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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