Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05cdc42328a04efa7e351bbf1806b301327e29c0600fabc4dce289791f1bac52

Tx prefix hash: fefb214b7f08b86d71a703389af29b814af1a67d5e7359c664ad7d5bfa2a58c4
Tx public key: e5a9c3e3c2118cb006f4944bac55fcadf420cd8315f964c1a783893c30ef2378
Timestamp: 1730911927 Timestamp [UCT]: 2024-11-06 16:52:07 Age [y:d:h:m:s]: 00:000:16:04:37
Block: 1147933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489 RingCT/type: yes/0
Extra: 01e5a9c3e3c2118cb006f4944bac55fcadf420cd8315f964c1a783893c30ef2378021100000001007f978a000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: f5102175c4c721e901802bee6960a96aa4fee3e0f1bc5ed2147dd446137e1c0c 0.600200000000 1632648 of 0

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": 1147943, "vin": [ { "gen": { "height": 1147933 } } ], "vout": [ { "amount": 600200000, "target": { "key": "f5102175c4c721e901802bee6960a96aa4fee3e0f1bc5ed2147dd446137e1c0c" } } ], "extra": [ 1, 229, 169, 195, 227, 194, 17, 140, 176, 6, 244, 148, 75, 172, 85, 252, 173, 244, 32, 205, 131, 21, 249, 100, 193, 167, 131, 137, 60, 48, 239, 35, 120, 2, 17, 0, 0, 0, 1, 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