Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657334420d1fc1b3e1b771c579bdfc705889b1b3b868e67f807d02eab1a5cc4e

Tx prefix hash: 1bb3dfb29e9a13130e92eba4510be0de5b103d6df73098470d5aaf646ec8e0f0
Tx public key: d14808326ea9651eb131ede2967bc30ccd1b233062dea872bd2392bcb3ae38d4
Timestamp: 1736315803 Timestamp [UCT]: 2025-01-08 05:56:43 Age [y:d:h:m:s]: 00:086:05:08:09
Block: 1192681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61403 RingCT/type: yes/0
Extra: 01d14808326ea9651eb131ede2967bc30ccd1b233062dea872bd2392bcb3ae38d4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb317a99a245f7a49874f144d1f3b80fabb9d99a04c8bf684b5e302e7f9a641 0.600000000000 1679236 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": 1192691, "vin": [ { "gen": { "height": 1192681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb317a99a245f7a49874f144d1f3b80fabb9d99a04c8bf684b5e302e7f9a641" } } ], "extra": [ 1, 209, 72, 8, 50, 110, 169, 101, 30, 177, 49, 237, 226, 150, 123, 195, 12, 205, 27, 35, 48, 98, 222, 168, 114, 189, 35, 146, 188, 179, 174, 56, 212, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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