Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13c1f4a667d779401e9c34184ff33886e14b97a514f71db94135bd5dcd6d1101

Tx prefix hash: 76c835e2ccaa7cb4e3baa4a7633706b2553a287c9c38cbe5f1d77cf1de1e3709
Tx public key: 1fdca2e9695636dc00268c3a16ce1e54a1685a2945331589a97b072a7facc03e
Timestamp: 1737569943 Timestamp [UCT]: 2025-01-22 18:19:03 Age [y:d:h:m:s]: 00:332:20:20:41
Block: 1203026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235472 RingCT/type: yes/0
Extra: 011fdca2e9695636dc00268c3a16ce1e54a1685a2945331589a97b072a7facc03e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3fa4a6f7bb0f76443cadb4660100ad08183177b2d70d0a9b679d4ce468f5eb8 0.600000000000 1689697 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": 1203036, "vin": [ { "gen": { "height": 1203026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3fa4a6f7bb0f76443cadb4660100ad08183177b2d70d0a9b679d4ce468f5eb8" } } ], "extra": [ 1, 31, 220, 162, 233, 105, 86, 54, 220, 0, 38, 140, 58, 22, 206, 30, 84, 161, 104, 90, 41, 69, 51, 21, 137, 169, 123, 7, 42, 127, 172, 192, 62, 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