Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50d2eeb89e49e38a7a1d6847f5a644746909de36959a6122c84ab581e8a2daed

Tx prefix hash: 21fa70d6cdf4ca6517dd68b25757ac603de014bacd86468e6460fe0faa9585e0
Tx public key: fc4c588ea8c2d47c7b944adc21a68580dc4a7829f62743de8ce6a34740e74cb6
Timestamp: 1738876589 Timestamp [UCT]: 2025-02-06 21:16:29 Age [y:d:h:m:s]: 00:318:15:25:50
Block: 1213624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225534 RingCT/type: yes/0
Extra: 01fc4c588ea8c2d47c7b944adc21a68580dc4a7829f62743de8ce6a34740e74cb6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d2a30f915641ff2723f7b3c62db59044b825dbdaccd2dccb01197eb4effd3a1 0.600000000000 1700403 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": 1213634, "vin": [ { "gen": { "height": 1213624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d2a30f915641ff2723f7b3c62db59044b825dbdaccd2dccb01197eb4effd3a1" } } ], "extra": [ 1, 252, 76, 88, 142, 168, 194, 212, 124, 123, 148, 74, 220, 33, 166, 133, 128, 220, 74, 120, 41, 246, 39, 67, 222, 140, 230, 163, 71, 64, 231, 76, 182, 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