Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c38530bdd05b7be0f5c391cd3339059989cb74ea0580ccc16a78539968d10af

Tx prefix hash: 3e8436fe54d4f2c4a4533d69ab17ab235b97a578a5ac21ebf7d3eaac338a3fe4
Tx public key: 6091e9293e9ff4d77221f255979cc8dd4092bfbfb0ff208a00a7695c1ccc8e0c
Timestamp: 1711574487 Timestamp [UCT]: 2024-03-27 21:21:27 Age [y:d:h:m:s]: 00:293:10:51:20
Block: 987724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210030 RingCT/type: yes/0
Extra: 016091e9293e9ff4d77221f255979cc8dd4092bfbfb0ff208a00a7695c1ccc8e0c02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5261627d54285c7b04f09da0b33f8d74501f92c9ea9a386e2644c20984c1c2ac 0.600000000000 1447981 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": 987734, "vin": [ { "gen": { "height": 987724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5261627d54285c7b04f09da0b33f8d74501f92c9ea9a386e2644c20984c1c2ac" } } ], "extra": [ 1, 96, 145, 233, 41, 62, 159, 244, 215, 114, 33, 242, 85, 151, 156, 200, 221, 64, 146, 191, 191, 176, 255, 32, 138, 0, 167, 105, 92, 28, 204, 142, 12, 2, 17, 0, 0, 0, 11, 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