Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cf2b0c9e13d288d68dd65b56407da8978ce91be4a388afbbb32fc4962a98e9

Tx prefix hash: 7d6c34776a6602c3cbf52bef644b98db928f93d2604ed5070b506fbf858806aa
Tx public key: c27d4721e57cefcc0d6d0e23945c6a44fdf93bde823cd43abe225d43a4ab16c6
Timestamp: 1721340173 Timestamp [UCT]: 2024-07-18 22:02:53 Age [y:d:h:m:s]: 01:195:13:48:18
Block: 1068673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398201 RingCT/type: yes/0
Extra: 01c27d4721e57cefcc0d6d0e23945c6a44fdf93bde823cd43abe225d43a4ab16c602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e670d0d161184d723a358cb87600c18873a1c46404d94afebe410f60dab1fb 0.600000000000 1539798 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": 1068683, "vin": [ { "gen": { "height": 1068673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e670d0d161184d723a358cb87600c18873a1c46404d94afebe410f60dab1fb" } } ], "extra": [ 1, 194, 125, 71, 33, 229, 124, 239, 204, 13, 109, 14, 35, 148, 92, 106, 68, 253, 249, 59, 222, 130, 60, 212, 58, 190, 34, 93, 67, 164, 171, 22, 198, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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