Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb47428c771245d1cd2b3f9630b3fc977cfb8fd847f71ece074909cfbc6e8f3

Tx prefix hash: 78366615e97e1bd277dacd3d91b219eda9047e1e2af323abd511dc3770255072
Tx public key: c0d56aa20d7e89224e821bf6857080d29662942703215a0afc229da39b088e92
Timestamp: 1677875229 Timestamp [UCT]: 2023-03-03 20:27:09 Age [y:d:h:m:s]: 02:033:16:59:25
Block: 709204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545659 RingCT/type: yes/0
Extra: 01c0d56aa20d7e89224e821bf6857080d29662942703215a0afc229da39b088e92021100000004835e4d22000000000000000000

1 output(s) for total of 2.742285348000 dcy

stealth address amount amount idx
00: 47ce8b6c21a84bf5e15f47ed0865f11e7006b59218eef5dc5f423df86d5b32d0 2.742285348000 1153165 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": 709214, "vin": [ { "gen": { "height": 709204 } } ], "vout": [ { "amount": 2742285348, "target": { "key": "47ce8b6c21a84bf5e15f47ed0865f11e7006b59218eef5dc5f423df86d5b32d0" } } ], "extra": [ 1, 192, 213, 106, 162, 13, 126, 137, 34, 78, 130, 27, 246, 133, 112, 128, 210, 150, 98, 148, 39, 3, 33, 90, 10, 252, 34, 157, 163, 155, 8, 142, 146, 2, 17, 0, 0, 0, 4, 131, 94, 77, 34, 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