Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea53efbb0aca657ecf69b90952ae1ecb69076d1e88fc8b706d9a75652e76baa7

Tx prefix hash: 559c81529fd68a47d9c0b73065f78eecc04b0b8e8701851e6cf690196ef1a349
Tx public key: 06df2332ebaf5e9a0f753e6d1561ca844b3caf9eac12167536eb091b80c02b8a
Timestamp: 1739602137 Timestamp [UCT]: 2025-02-15 06:48:57 Age [y:d:h:m:s]: 00:279:00:55:21
Block: 1219590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197209 RingCT/type: yes/0
Extra: 0106df2332ebaf5e9a0f753e6d1561ca844b3caf9eac12167536eb091b80c02b8a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c14b89efa50f755486c99ec2ee59697b3e34579553d5e1ddaf40e1bce40d5d4 0.600000000000 1706419 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": 1219600, "vin": [ { "gen": { "height": 1219590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c14b89efa50f755486c99ec2ee59697b3e34579553d5e1ddaf40e1bce40d5d4" } } ], "extra": [ 1, 6, 223, 35, 50, 235, 175, 94, 154, 15, 117, 62, 109, 21, 97, 202, 132, 75, 60, 175, 158, 172, 18, 22, 117, 54, 235, 9, 27, 128, 192, 43, 138, 2, 17, 0, 0, 0, 1, 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