Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f3ffb0588ca85703a7601c1c5d92557be8991e8ff0c080333b815236c4b29ef

Tx prefix hash: 9e52a027614cec6c5b27ba92364af505a4f1f45296bb7ca06acb214b1de6d2f5
Tx public key: b168714d1c4b6d4c56f2361805979a217e4c654eaceb2a9e12c279e888a0af51
Timestamp: 1722620890 Timestamp [UCT]: 2024-08-02 17:48:10 Age [y:d:h:m:s]: 00:250:18:58:08
Block: 1079281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179141 RingCT/type: yes/0
Extra: 01b168714d1c4b6d4c56f2361805979a217e4c654eaceb2a9e12c279e888a0af5102110000000a91e13c04000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 2b52746c8c18bbdccf4dcb90f221fbcf34d3ad8d477d96ca37cb40660f82e78b 0.615590000000 1552164 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": 1079291, "vin": [ { "gen": { "height": 1079281 } } ], "vout": [ { "amount": 615590000, "target": { "key": "2b52746c8c18bbdccf4dcb90f221fbcf34d3ad8d477d96ca37cb40660f82e78b" } } ], "extra": [ 1, 177, 104, 113, 77, 28, 75, 109, 76, 86, 242, 54, 24, 5, 151, 154, 33, 126, 76, 101, 78, 172, 235, 42, 158, 18, 194, 121, 232, 136, 160, 175, 81, 2, 17, 0, 0, 0, 10, 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