Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db24875b7e6bdfa5055df5fa49885fe544417f32fe2513f8fefc16e91476d40

Tx prefix hash: fd5e990062b3ff866600bb2b498170f1de53b7e0872e193d7f30ee5785ba1466
Tx public key: 1f5ffad6865498c80c73f5846f5e4741d7410d0ac214a2c013a05928c7ba0b02
Timestamp: 1723774397 Timestamp [UCT]: 2024-08-16 02:13:17 Age [y:d:h:m:s]: 00:230:12:01:29
Block: 1088856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164600 RingCT/type: yes/0
Extra: 011f5ffad6865498c80c73f5846f5e4741d7410d0ac214a2c013a05928c7ba0b02021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a396dd2f4bf3bce3f1b085018f5fe421bb4d0dddcf4867a645afa8b1ade7ef2 0.600000000000 1563475 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": 1088866, "vin": [ { "gen": { "height": 1088856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a396dd2f4bf3bce3f1b085018f5fe421bb4d0dddcf4867a645afa8b1ade7ef2" } } ], "extra": [ 1, 31, 95, 250, 214, 134, 84, 152, 200, 12, 115, 245, 132, 111, 94, 71, 65, 215, 65, 13, 10, 194, 20, 162, 192, 19, 160, 89, 40, 199, 186, 11, 2, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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