Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc685f646357698219889221c9cde2907ba269dc57a0e02e8abcfb999763fa9

Tx prefix hash: 466d2dbc78cc873b9e29509c872b31997105e6abb2ae78cce90a26082caeb0d5
Tx public key: b9b64e3edc9b7a716d39e92497d41669b5f15655c3015e70839d953fe09c5126
Timestamp: 1608927176 Timestamp [UCT]: 2020-12-25 20:12:56 Age [y:d:h:m:s]: 03:315:18:41:54
Block: 169374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977778 RingCT/type: yes/0
Extra: 01b9b64e3edc9b7a716d39e92497d41669b5f15655c3015e70839d953fe09c51260211000001364ea414e5000000000000000000

1 output(s) for total of 168.581277014000 dcy

stealth address amount amount idx
00: 758c4c3163ce3cea9d3f153e9dafb137b2e35d8727610de77d987ac69a7bf0cd 168.581277014000 316065 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": 169384, "vin": [ { "gen": { "height": 169374 } } ], "vout": [ { "amount": 168581277014, "target": { "key": "758c4c3163ce3cea9d3f153e9dafb137b2e35d8727610de77d987ac69a7bf0cd" } } ], "extra": [ 1, 185, 182, 78, 62, 220, 155, 122, 113, 109, 57, 233, 36, 151, 212, 22, 105, 181, 241, 86, 85, 195, 1, 94, 112, 131, 157, 149, 63, 224, 156, 81, 38, 2, 17, 0, 0, 1, 54, 78, 164, 20, 229, 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