Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f372b890081219361475f2af5cab0743c2d566dba5bad27192b972f2b7e40f

Tx prefix hash: 0d595b71b76b2ab22991a2593624db5bb75d7b04c4ef4b3034e3a55364ac0ae1
Tx public key: 2b0010fb0d8696e9591124f807ff9cf6ad3cfb091e9085e92624fb9aa7a696bd
Timestamp: 1726479717 Timestamp [UCT]: 2024-09-16 09:41:57 Age [y:d:h:m:s]: 00:205:18:39:42
Block: 1111277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146899 RingCT/type: yes/0
Extra: 012b0010fb0d8696e9591124f807ff9cf6ad3cfb091e9085e92624fb9aa7a696bd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409563aa78d46129d51077271bab6543d4fe87dded7ec67e4a49c265b16861d9 0.600000000000 1590180 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": 1111287, "vin": [ { "gen": { "height": 1111277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409563aa78d46129d51077271bab6543d4fe87dded7ec67e4a49c265b16861d9" } } ], "extra": [ 1, 43, 0, 16, 251, 13, 134, 150, 233, 89, 17, 36, 248, 7, 255, 156, 246, 173, 60, 251, 9, 30, 144, 133, 233, 38, 36, 251, 154, 167, 166, 150, 189, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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