Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8335c2aa0789e9e197a027e9ea78e26021dcb2fd1388d06fb47c15cfdc0863d6

Tx prefix hash: acd4d579a831ee781c8baf8cb7aea78fcdf11447fa7fd306343237f3bde4a6c7
Tx public key: f6a169e49d05a5bd8d931e361c6a111d5f5ccfd62a53c6465c3168b39c15780d
Timestamp: 1577374691 Timestamp [UCT]: 2019-12-26 15:38:11 Age [y:d:h:m:s]: 05:004:07:11:17
Block: 32278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153042 RingCT/type: yes/0
Extra: 01f6a169e49d05a5bd8d931e361c6a111d5f5ccfd62a53c6465c3168b39c15780d0211000000034943cd9f000000000000000000

1 output(s) for total of 479.789175573000 dcy

stealth address amount amount idx
00: f7479904848f22dd67b6babf18e5919f8ca93e5a971870d366656d8376ce5f8f 479.789175573000 53663 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": 32288, "vin": [ { "gen": { "height": 32278 } } ], "vout": [ { "amount": 479789175573, "target": { "key": "f7479904848f22dd67b6babf18e5919f8ca93e5a971870d366656d8376ce5f8f" } } ], "extra": [ 1, 246, 161, 105, 228, 157, 5, 165, 189, 141, 147, 30, 54, 28, 106, 17, 29, 95, 92, 207, 214, 42, 83, 198, 70, 92, 49, 104, 179, 156, 21, 120, 13, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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