Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2260d7ac66c01670242da4732730bdd23e9a1bdbccac1c596f20ec1fe04c7f7

Tx prefix hash: ab3e51f5fa71f193992997e397331b6061deab72b93da88fcb934f7f06d6add7
Tx public key: 00497a2daf6ffa7612982c8c80b8e250fd31d7cb0883efb4916005a92268ca27
Timestamp: 1744648993 Timestamp [UCT]: 2025-04-14 16:43:13 Age [y:d:h:m:s]: 00:220:07:41:42
Block: 1261406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155176 RingCT/type: yes/0
Extra: 0100497a2daf6ffa7612982c8c80b8e250fd31d7cb0883efb4916005a92268ca270211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7c00b3d27c2dbc2549b8fca9cb7f20f235458dc24f1fab3cdd65c5189e8153 0.600000000000 1748575 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": 1261416, "vin": [ { "gen": { "height": 1261406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7c00b3d27c2dbc2549b8fca9cb7f20f235458dc24f1fab3cdd65c5189e8153" } } ], "extra": [ 1, 0, 73, 122, 45, 175, 111, 250, 118, 18, 152, 44, 140, 128, 184, 226, 80, 253, 49, 215, 203, 8, 131, 239, 180, 145, 96, 5, 169, 34, 104, 202, 39, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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