Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 532f7c0bf882a23ed637c36cc36cffb13f387d11574a444dade98ffc638cb328

Tx prefix hash: 3f4b3ad6a0275aa9bea7b23a09d98c4c2ad13c9e69c999c3c7538d89188c2959
Tx public key: 09e911710c719d02aa7b04d8dc072544bfb526ea3cb121881926d9fec9395c05
Timestamp: 1587144496 Timestamp [UCT]: 2020-04-17 17:28:16 Age [y:d:h:m:s]: 05:201:14:40:51
Block: 93739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1310923 RingCT/type: yes/0
Extra: 0109e911710c719d02aa7b04d8dc072544bfb526ea3cb121881926d9fec9395c050211000006ab37fb5df4000000000000000000

1 output(s) for total of 300.195757391000 dcy

stealth address amount amount idx
00: 37f2b0a178dba4a12685a7e834a8d3a6ad2cc7d115b4e2b48c3b0866b583a7a2 300.195757391000 166831 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": 93749, "vin": [ { "gen": { "height": 93739 } } ], "vout": [ { "amount": 300195757391, "target": { "key": "37f2b0a178dba4a12685a7e834a8d3a6ad2cc7d115b4e2b48c3b0866b583a7a2" } } ], "extra": [ 1, 9, 233, 17, 113, 12, 113, 157, 2, 170, 123, 4, 216, 220, 7, 37, 68, 191, 181, 38, 234, 60, 177, 33, 136, 25, 38, 217, 254, 201, 57, 92, 5, 2, 17, 0, 0, 6, 171, 55, 251, 93, 244, 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