Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf57749757a63179bba75e130692888dd8939c4e96222e125f2c1cd02c6034c9

Tx prefix hash: bfa593fb4e14ad3dad3dd6d6acf448d7a41e35dd13746abd0595c63c51aee648
Tx public key: dc1c6baf4eabc7d88a83f166f28108000015efc67f724e3a11c15aedd9693324
Timestamp: 1658027894 Timestamp [UCT]: 2022-07-17 03:18:14 Age [y:d:h:m:s]: 02:166:04:45:25
Block: 545447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640139 RingCT/type: yes/0
Extra: 01dc1c6baf4eabc7d88a83f166f28108000015efc67f724e3a11c15aedd9693324021100000011bf7ee4e7000000000000000000

1 output(s) for total of 9.565502777000 dcy

stealth address amount amount idx
00: f382c2db7664b9eacb0c86791cbb414ac0130a46ce0c43a8d9640e55c1ef924a 9.565502777000 976342 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": 545457, "vin": [ { "gen": { "height": 545447 } } ], "vout": [ { "amount": 9565502777, "target": { "key": "f382c2db7664b9eacb0c86791cbb414ac0130a46ce0c43a8d9640e55c1ef924a" } } ], "extra": [ 1, 220, 28, 107, 175, 78, 171, 199, 216, 138, 131, 241, 102, 242, 129, 8, 0, 0, 21, 239, 198, 127, 114, 78, 58, 17, 193, 90, 237, 217, 105, 51, 36, 2, 17, 0, 0, 0, 17, 191, 126, 228, 231, 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