Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3848043238573181ccb0f5d319d85d81f0ddc1d90165b0baa5c3be7ac26f7b7

Tx prefix hash: f30c9222e1ced180cb8bd8452adc6af9a206af126c8f743c28144820ddb3e012
Tx public key: e3831cabd735138b1319824c2ed5d962735c64911cc51c4f966d8e75b4843969
Timestamp: 1714452839 Timestamp [UCT]: 2024-04-30 04:53:59 Age [y:d:h:m:s]: 00:144:07:50:34
Block: 1011564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103390 RingCT/type: yes/0
Extra: 01e3831cabd735138b1319824c2ed5d962735c64911cc51c4f966d8e75b48439690211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: bb1d120213e8c3d8a5073d7d071a65690a46e12cb2d6f0180d21417af8026edc 0.615580000000 1473826 of 0

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": 1011574, "vin": [ { "gen": { "height": 1011564 } } ], "vout": [ { "amount": 615580000, "target": { "key": "bb1d120213e8c3d8a5073d7d071a65690a46e12cb2d6f0180d21417af8026edc" } } ], "extra": [ 1, 227, 131, 28, 171, 215, 53, 19, 139, 19, 25, 130, 76, 46, 213, 217, 98, 115, 92, 100, 145, 28, 197, 28, 79, 150, 109, 142, 117, 180, 132, 57, 105, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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