Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88399400d9fca67e96465e51fbfb13a6e4691e846e603ae1a9a3b9e0b51656d9

Tx prefix hash: 7357af1b3ac38bed2908c5da3243658ffb339a775d07d870bd37d691de2eac8c
Tx public key: f754db0e750b5c3d20a2686373d64043a7b6fc9e93a32a3ad604d0702090713a
Timestamp: 1718770429 Timestamp [UCT]: 2024-06-19 04:13:49 Age [y:d:h:m:s]: 01:138:00:15:36
Block: 1047363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357187 RingCT/type: yes/0
Extra: 01f754db0e750b5c3d20a2686373d64043a7b6fc9e93a32a3ad604d0702090713a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9b3e56efc93e4ab1f61e6601f8af9a9429d8234ef944fc43a26c6a91c72e6c 0.600000000000 1517182 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": 1047373, "vin": [ { "gen": { "height": 1047363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9b3e56efc93e4ab1f61e6601f8af9a9429d8234ef944fc43a26c6a91c72e6c" } } ], "extra": [ 1, 247, 84, 219, 14, 117, 11, 92, 61, 32, 162, 104, 99, 115, 214, 64, 67, 167, 182, 252, 158, 147, 163, 42, 58, 214, 4, 208, 112, 32, 144, 113, 58, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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