Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d9b9c1d8c52a0b4fe85eb60e1094a9a7e5d59047fccee0994c686141ae047f3

Tx prefix hash: 9d09f349a1f2aaf5bf8f1f7092ef11c45dc06ca8cd1a1e0b7ca6bfd8e5da9d8d
Tx public key: f0337ff19516b05340ac36d50621dd80bd5f709d4306ac26b592329d5d7f8e8a
Timestamp: 1696876415 Timestamp [UCT]: 2023-10-09 18:33:35 Age [y:d:h:m:s]: 02:038:02:24:47
Block: 866060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546854 RingCT/type: yes/0
Extra: 01f0337ff19516b05340ac36d50621dd80bd5f709d4306ac26b592329d5d7f8e8a02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.828674041000 dcy

stealth address amount amount idx
00: 722790b32f0143472057cfc4e4212eb9a800580888f4b1038399cac45a17c198 0.828674041000 1320628 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": 866070, "vin": [ { "gen": { "height": 866060 } } ], "vout": [ { "amount": 828674041, "target": { "key": "722790b32f0143472057cfc4e4212eb9a800580888f4b1038399cac45a17c198" } } ], "extra": [ 1, 240, 51, 127, 241, 149, 22, 176, 83, 64, 172, 54, 213, 6, 33, 221, 128, 189, 95, 112, 157, 67, 6, 172, 38, 181, 146, 50, 157, 93, 127, 142, 138, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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