Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5dee19734b3b834eb051c0b559ee8918bc8a9c67163b7af3b8020e962a7e39b

Tx prefix hash: 79dd65ca2a38ebaad229d0f7c41460385279bf5b7db2cad9f6876460abc8439f
Tx public key: 3d2a301fd96a8e57171d1041cd13c9518a68e7e7149ac9cfd108fb44524d5dd2
Timestamp: 1588732259 Timestamp [UCT]: 2020-05-06 02:30:59 Age [y:d:h:m:s]: 04:308:19:28:46
Block: 98539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137285 RingCT/type: yes/0
Extra: 013d2a301fd96a8e57171d1041cd13c9518a68e7e7149ac9cfd108fb44524d5dd202110000008237fb5df4000000000000000000

1 output(s) for total of 289.401082703000 dcy

stealth address amount amount idx
00: 334a80d5ef45f191d209cb5ef6c137eb32e36e0a96a591f2c81ae7051443c3a0 289.401082703000 174201 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": 98549, "vin": [ { "gen": { "height": 98539 } } ], "vout": [ { "amount": 289401082703, "target": { "key": "334a80d5ef45f191d209cb5ef6c137eb32e36e0a96a591f2c81ae7051443c3a0" } } ], "extra": [ 1, 61, 42, 48, 31, 217, 106, 142, 87, 23, 29, 16, 65, 205, 19, 201, 81, 138, 104, 231, 231, 20, 154, 201, 207, 209, 8, 251, 68, 82, 77, 93, 210, 2, 17, 0, 0, 0, 130, 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