Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede3fc071921aa6c3321a28aba7666f4ac35cadb7f4a0ba671aa7f12dda71c2a

Tx prefix hash: 25be3c047db8bdbb149e89d07b18b94e19e78436ebd84898fa717c2c770579a1
Tx public key: ddb83854607259cc77dbbccca400087dc7c3e6fb17f6d590e8cdc937d870f56a
Timestamp: 1577609262 Timestamp [UCT]: 2019-12-29 08:47:42 Age [y:d:h:m:s]: 05:099:01:12:09
Block: 34170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220593 RingCT/type: yes/0
Extra: 01ddb83854607259cc77dbbccca400087dc7c3e6fb17f6d590e8cdc937d870f56a02110000000c4943cd9f000000000000000000

1 output(s) for total of 472.984987526000 dcy

stealth address amount amount idx
00: 288124fc916db883c63ee412ce8e31ddaceb072a0f47bd4101c25b7f448cb8f5 472.984987526000 57520 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": 34180, "vin": [ { "gen": { "height": 34170 } } ], "vout": [ { "amount": 472984987526, "target": { "key": "288124fc916db883c63ee412ce8e31ddaceb072a0f47bd4101c25b7f448cb8f5" } } ], "extra": [ 1, 221, 184, 56, 84, 96, 114, 89, 204, 119, 219, 188, 204, 164, 0, 8, 125, 199, 195, 230, 251, 23, 246, 213, 144, 232, 205, 201, 55, 216, 112, 245, 106, 2, 17, 0, 0, 0, 12, 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