Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6436e410213fe24490a67b4cae5dc0ac1049308443fc74ac01604eac122aa9b9

Tx prefix hash: 8aa770621b13d46cfabcd464c1185fa2b267d57e5e243a40159ec0addd19b71b
Tx public key: 9dbc77f4c70febca90fbfa734aabaf5028b7df6c0c5ae83652f0f467d38fe562
Timestamp: 1643532139 Timestamp [UCT]: 2022-01-30 08:42:19 Age [y:d:h:m:s]: 03:044:06:49:44
Block: 428361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 810852 RingCT/type: yes/0
Extra: 019dbc77f4c70febca90fbfa734aabaf5028b7df6c0c5ae83652f0f467d38fe5620211000000072e6b1fd5000000000000000000

1 output(s) for total of 23.370203622000 dcy

stealth address amount amount idx
00: ac47d82ff68a3aff5d38de987066aa419d983b2dd20fe4d02549ad4e96b0c824 23.370203622000 837741 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": 428371, "vin": [ { "gen": { "height": 428361 } } ], "vout": [ { "amount": 23370203622, "target": { "key": "ac47d82ff68a3aff5d38de987066aa419d983b2dd20fe4d02549ad4e96b0c824" } } ], "extra": [ 1, 157, 188, 119, 244, 199, 15, 235, 202, 144, 251, 250, 115, 74, 171, 175, 80, 40, 183, 223, 108, 12, 90, 232, 54, 82, 240, 244, 103, 211, 143, 229, 98, 2, 17, 0, 0, 0, 7, 46, 107, 31, 213, 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