Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1cbcf013e701e83f52b8edb452cfd6abdad44b5670238a1732ef59670a04249

Tx prefix hash: 1943306ace62590b0c6787a92eb7cd001240b32ca0f6e838f4fa05e496a02049
Tx public key: 4c33fc6e3df19bfb317def1f0aa34fc52ada8dc939678a90fbc1ee98fa6871ec
Timestamp: 1732504782 Timestamp [UCT]: 2024-11-25 03:19:42 Age [y:d:h:m:s]: 00:204:09:54:41
Block: 1161132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145842 RingCT/type: yes/0
Extra: 014c33fc6e3df19bfb317def1f0aa34fc52ada8dc939678a90fbc1ee98fa6871ec02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 018aa7e8c743cfb15b4ed3b039414b98fcea1c6cb2f502213d77491a18f9c95f 0.600000000000 1646783 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": 1161142, "vin": [ { "gen": { "height": 1161132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "018aa7e8c743cfb15b4ed3b039414b98fcea1c6cb2f502213d77491a18f9c95f" } } ], "extra": [ 1, 76, 51, 252, 110, 61, 241, 155, 251, 49, 125, 239, 31, 10, 163, 79, 197, 42, 218, 141, 201, 57, 103, 138, 144, 251, 193, 238, 152, 250, 104, 113, 236, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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