Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf61370bf3d690c7d5df29c0d914120ce8160bb89a9f4782d9fbfc29a870775a

Tx prefix hash: e057b8db29eafb7a993e21a7f41d1e04cd7469ec9fa4b34fa8fd7022b2d0f36a
Tx public key: 719bcde9cafee0cd4204b58dbadf2d78ceb8d7e8ac11baf5059b611a1f36e060
Timestamp: 1580977987 Timestamp [UCT]: 2020-02-06 08:33:07 Age [y:d:h:m:s]: 04:274:02:55:24
Block: 59758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087292 RingCT/type: yes/0
Extra: 01719bcde9cafee0cd4204b58dbadf2d78ceb8d7e8ac11baf5059b611a1f36e060021100000003724f989b000000000000000000

1 output(s) for total of 389.043136558000 dcy

stealth address amount amount idx
00: 5cf08a0499845f8f21d0bf9a13a86a58ffd84eceb6a1b7fda6362b782e19779f 389.043136558000 110260 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": 59768, "vin": [ { "gen": { "height": 59758 } } ], "vout": [ { "amount": 389043136558, "target": { "key": "5cf08a0499845f8f21d0bf9a13a86a58ffd84eceb6a1b7fda6362b782e19779f" } } ], "extra": [ 1, 113, 155, 205, 233, 202, 254, 224, 205, 66, 4, 181, 141, 186, 223, 45, 120, 206, 184, 215, 232, 172, 17, 186, 245, 5, 155, 97, 26, 31, 54, 224, 96, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 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