Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 841b7a732d56d16e14911699270ed68de5e8e3f31b36e7675108d7309312fc0a

Tx prefix hash: c2e31b267eae8b65d9acec10290a866054343bc815f291d27e09409e0524d23c
Tx public key: 46c9c67f504569e78e4f30e9b19ae7f760e1f20a03c4ebd0e36b7f0d0c807f16
Timestamp: 1726116035 Timestamp [UCT]: 2024-09-12 04:40:35 Age [y:d:h:m:s]: 00:164:04:23:32
Block: 1108253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117142 RingCT/type: yes/0
Extra: 0146c9c67f504569e78e4f30e9b19ae7f760e1f20a03c4ebd0e36b7f0d0c807f1602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aed0cded3dd7c42c4b15ce533163709667d75f37b05d5f3916a2264dfc3ca213 0.600000000000 1586084 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": 1108263, "vin": [ { "gen": { "height": 1108253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aed0cded3dd7c42c4b15ce533163709667d75f37b05d5f3916a2264dfc3ca213" } } ], "extra": [ 1, 70, 201, 198, 127, 80, 69, 105, 231, 142, 79, 48, 233, 177, 154, 231, 247, 96, 225, 242, 10, 3, 196, 235, 208, 227, 107, 127, 13, 12, 128, 127, 22, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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