Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f652c5a2a671da1f95b9c092b3173511b3b374a014c23d18901a52c3eb50b070

Tx prefix hash: c33ad7361c99534e5c81ba793968fac9ddcce403f3d49d42d6acc0e84fc76acb
Tx public key: 9b499aab18dc70d5489a0f910393d3b932550a553f5638776d86b24127a721e8
Timestamp: 1722582075 Timestamp [UCT]: 2024-08-02 07:01:15 Age [y:d:h:m:s]: 00:320:11:26:11
Block: 1078962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228861 RingCT/type: yes/0
Extra: 019b499aab18dc70d5489a0f910393d3b932550a553f5638776d86b24127a721e802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf045f17e594df6715d183b394fd2d34187d2f22ce1cfd6fa970705bee6abbe 0.600000000000 1551709 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": 1078972, "vin": [ { "gen": { "height": 1078962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf045f17e594df6715d183b394fd2d34187d2f22ce1cfd6fa970705bee6abbe" } } ], "extra": [ 1, 155, 73, 154, 171, 24, 220, 112, 213, 72, 154, 15, 145, 3, 147, 211, 185, 50, 85, 10, 85, 63, 86, 56, 119, 109, 134, 178, 65, 39, 167, 33, 232, 2, 17, 0, 0, 0, 10, 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