Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd26796d04e6ea3abac7403357d0e67c7897024722c5a3f4f09986a6517cef2e

Tx prefix hash: 452f6bb7d52933a705cb0c743d61a8f7fff9229176628c4d92a5aa14efda2fbb
Tx public key: 534b362045ce2b8558bfa6dc6ad70271aaedd05133c768798692049eaaa341d4
Timestamp: 1673455712 Timestamp [UCT]: 2023-01-11 16:48:32 Age [y:d:h:m:s]: 02:020:15:42:45
Block: 672537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536405 RingCT/type: yes/0
Extra: 01534b362045ce2b8558bfa6dc6ad70271aaedd05133c768798692049eaaa341d40211000000018b7b6602000000000000000000

1 output(s) for total of 3.627485533000 dcy

stealth address amount amount idx
00: ccf28056f1bfc9d9dc00dc738fec00c189b70327b25ada4d1fb47f654776a206 3.627485533000 1114094 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": 672547, "vin": [ { "gen": { "height": 672537 } } ], "vout": [ { "amount": 3627485533, "target": { "key": "ccf28056f1bfc9d9dc00dc738fec00c189b70327b25ada4d1fb47f654776a206" } } ], "extra": [ 1, 83, 75, 54, 32, 69, 206, 43, 133, 88, 191, 166, 220, 106, 215, 2, 113, 170, 237, 208, 81, 51, 199, 104, 121, 134, 146, 4, 158, 170, 163, 65, 212, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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