Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351edeca0b357089f6d7869c6b74d4380abec42b3b089b2fcc6ffa5e73d9e82b

Tx prefix hash: 5f86d844e2c5410ff1b9219607cc737bac17f7797b11a2c65be8fcdeef0c60f9
Tx public key: 01d890c1db846ab23d52e1dc388e427c5e4ebe0c9bf10e8f7c01f67b247c9b2d
Timestamp: 1702845085 Timestamp [UCT]: 2023-12-17 20:31:25 Age [y:d:h:m:s]: 01:033:08:45:29
Block: 915334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285154 RingCT/type: yes/0
Extra: 0101d890c1db846ab23d52e1dc388e427c5e4ebe0c9bf10e8f7c01f67b247c9b2d02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d08f29165a399aa635ca4ce199a925b847f4fe9a84019a3f87eb31d6e933c6c 0.600000000000 1372728 of 15

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": 915344, "vin": [ { "gen": { "height": 915334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d08f29165a399aa635ca4ce199a925b847f4fe9a84019a3f87eb31d6e933c6c" } } ], "extra": [ 1, 1, 216, 144, 193, 219, 132, 106, 178, 61, 82, 225, 220, 56, 142, 66, 124, 94, 78, 190, 12, 155, 241, 14, 143, 124, 1, 246, 123, 36, 124, 155, 45, 2, 17, 0, 0, 0, 1, 51, 175, 153, 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