Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830f1ed1f236b6d5c9f3207feb3ef7f7a60d8f312617b7e596a1a170d173655e

Tx prefix hash: 80bcebb6902b133fbf215d664f39d55741a6879ed88f01d0ebea67129c191fb4
Tx public key: 371c33435eea312b4d27254deccac6232bdf4e5b3fd7d92baa9949e5bd38c99d
Timestamp: 1733721804 Timestamp [UCT]: 2024-12-09 05:23:24 Age [y:d:h:m:s]: 00:028:02:53:22
Block: 1171213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20121 RingCT/type: yes/0
Extra: 01371c33435eea312b4d27254deccac6232bdf4e5b3fd7d92baa9949e5bd38c99d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ca65670e3d1b15312574f908279e9ad74e601b005dab615d2c010a490184af 0.600000000000 1656952 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": 1171223, "vin": [ { "gen": { "height": 1171213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ca65670e3d1b15312574f908279e9ad74e601b005dab615d2c010a490184af" } } ], "extra": [ 1, 55, 28, 51, 67, 94, 234, 49, 43, 77, 39, 37, 77, 236, 202, 198, 35, 43, 223, 78, 91, 63, 215, 217, 43, 170, 153, 73, 229, 189, 56, 201, 157, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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