Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48debcee4397b7ef94e81e73f6c0cc479de14f73bcc72acb93fc051470c352ec

Tx prefix hash: 96b226675b1f31761cee73b972f9eb2ebad9d31460f7baa75e5b1a29f444d13f
Tx public key: 29dc1db6fbb175f5e540c2ebbdeee5ceb635501bdc29938a1e02044d1ab0dccd
Timestamp: 1707843469 Timestamp [UCT]: 2024-02-13 16:57:49 Age [y:d:h:m:s]: 00:288:21:46:19
Block: 956766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206859 RingCT/type: yes/0
Extra: 0129dc1db6fbb175f5e540c2ebbdeee5ceb635501bdc29938a1e02044d1ab0dccd0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68d504a551504f4f7c7470610116de9c925c66139663b4df27fd856f35d1655 0.600000000000 1416076 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": 956776, "vin": [ { "gen": { "height": 956766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68d504a551504f4f7c7470610116de9c925c66139663b4df27fd856f35d1655" } } ], "extra": [ 1, 41, 220, 29, 182, 251, 177, 117, 245, 229, 64, 194, 235, 189, 238, 229, 206, 182, 53, 80, 27, 220, 41, 147, 138, 30, 2, 4, 77, 26, 176, 220, 205, 2, 17, 0, 0, 0, 8, 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