Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592c349185e4c99ecdc04665cada41fc4af6edcc0c4502514d6b91d2c730583a

Tx prefix hash: c5f5da6fa975cf3c725345107979685a994d956f045b1b2078bb2b1e68ffe9e9
Tx public key: 2a0f6c1539c7565b32d8c3912d922023269956beaa36fcdc9da9b07717dbbbaf
Timestamp: 1714136491 Timestamp [UCT]: 2024-04-26 13:01:31 Age [y:d:h:m:s]: 00:202:22:28:11
Block: 1008945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145269 RingCT/type: yes/0
Extra: 012a0f6c1539c7565b32d8c3912d922023269956beaa36fcdc9da9b07717dbbbaf0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d2f18716791ec68c0b92e4d00d8d004e51732906ca9a3b0c4a47cc5c3003097 0.600000000000 1470465 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": 1008955, "vin": [ { "gen": { "height": 1008945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d2f18716791ec68c0b92e4d00d8d004e51732906ca9a3b0c4a47cc5c3003097" } } ], "extra": [ 1, 42, 15, 108, 21, 57, 199, 86, 91, 50, 216, 195, 145, 45, 146, 32, 35, 38, 153, 86, 190, 170, 54, 252, 220, 157, 169, 176, 119, 23, 219, 187, 175, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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