Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cabaa276d333556fd9fd2ec8bf7b7bb156e946b69643c20d1c91d5298222aa2

Tx prefix hash: 6c497518afbd87baa6456e9757d33f0ebf3064dd13aa9bdd8fcd23bf9f4da94c
Tx public key: 28d3e88bb4b7d10683c30252032d1288bf77a13b3ea4ffaac334ef4cf02b4cf2
Timestamp: 1672912887 Timestamp [UCT]: 2023-01-05 10:01:27 Age [y:d:h:m:s]: 02:090:01:12:16
Block: 668036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586050 RingCT/type: yes/0
Extra: 0128d3e88bb4b7d10683c30252032d1288bf77a13b3ea4ffaac334ef4cf02b4cf202110000000152542ceb000000000000000000

1 output(s) for total of 3.754217045000 dcy

stealth address amount amount idx
00: a22df6478f1f7dc648f59f6c8f1d996380eeb8352bebe3ef45cd7949ee02a6ec 3.754217045000 1109265 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": 668046, "vin": [ { "gen": { "height": 668036 } } ], "vout": [ { "amount": 3754217045, "target": { "key": "a22df6478f1f7dc648f59f6c8f1d996380eeb8352bebe3ef45cd7949ee02a6ec" } } ], "extra": [ 1, 40, 211, 232, 139, 180, 183, 209, 6, 131, 195, 2, 82, 3, 45, 18, 136, 191, 119, 161, 59, 62, 164, 255, 170, 195, 52, 239, 76, 240, 43, 76, 242, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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