Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483550830ee9bcfa9eec6863ef3b2b75ea78c6891d9e15f21bd1fae714b8e8d8

Tx prefix hash: 8778678d5385f525307ccce5d36008f9f33322c5b6664c400e9a20f81fede02a
Tx public key: 279ae1f81a2a528eb1ddde1df929f36df50be7ae3e5d72bf903841a2f13f78b3
Timestamp: 1735372066 Timestamp [UCT]: 2024-12-28 07:47:46 Age [y:d:h:m:s]: 00:124:03:29:30
Block: 1184872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88522 RingCT/type: yes/0
Extra: 01279ae1f81a2a528eb1ddde1df929f36df50be7ae3e5d72bf903841a2f13f78b30211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b31e963e2602a54a1c5c95790476621a01daa403ebd3904f7ed3705a93a5f65 0.600000000000 1671331 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": 1184882, "vin": [ { "gen": { "height": 1184872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b31e963e2602a54a1c5c95790476621a01daa403ebd3904f7ed3705a93a5f65" } } ], "extra": [ 1, 39, 154, 225, 248, 26, 42, 82, 142, 177, 221, 222, 29, 249, 41, 243, 109, 245, 11, 231, 174, 62, 93, 114, 191, 144, 56, 65, 162, 241, 63, 120, 179, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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