Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c3219c37e82870f1df96d2e1b8ea9de15e38f15f489943cd9e97e2cb0d3371b

Tx prefix hash: 2e9b8c401b9b2e6ddad0eaccfefbba4e84ade5daf0c439088e19b4cbd268b036
Tx public key: 876c1c9c47c60e6e1058f78c4dd266e5ecc4641f2bdf171836bc3dd1e11e4c25
Timestamp: 1728831119 Timestamp [UCT]: 2024-10-13 14:51:59 Age [y:d:h:m:s]: 00:004:23:36:27
Block: 1130773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3569 RingCT/type: yes/0
Extra: 01876c1c9c47c60e6e1058f78c4dd266e5ecc4641f2bdf171836bc3dd1e11e4c25021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7305471aaa55e31153b4ebf58d7e25efdf4dbe880e0e7b0ee033e3a2f5dde25d 0.600000000000 1613654 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": 1130783, "vin": [ { "gen": { "height": 1130773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7305471aaa55e31153b4ebf58d7e25efdf4dbe880e0e7b0ee033e3a2f5dde25d" } } ], "extra": [ 1, 135, 108, 28, 156, 71, 198, 14, 110, 16, 88, 247, 140, 77, 210, 102, 229, 236, 196, 100, 31, 43, 223, 23, 24, 54, 188, 61, 209, 225, 30, 76, 37, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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