Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f80f1f5f6159cf4ef41e62e173ea58153a90389b29b90631a9c6177e431571

Tx prefix hash: 98ceb70b3cfe80920f0558fb87b389ef53099c346dea3453d4d2d03f1cab5bca
Tx public key: 158efc4c144b1db50c18fd30dcdb66ad19647949a8a0e5b38cebfb7216b35a4d
Timestamp: 1673949363 Timestamp [UCT]: 2023-01-17 09:56:03 Age [y:d:h:m:s]: 02:082:16:52:36
Block: 676635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580769 RingCT/type: yes/0
Extra: 01158efc4c144b1db50c18fd30dcdb66ad19647949a8a0e5b38cebfb7216b35a4d0211000000025ec35160000000000000000000

1 output(s) for total of 3.515825470000 dcy

stealth address amount amount idx
00: d6c1a193ba9b34427f28b05fc3de24fa50eebffb602f3c9aa8fc348778daacfa 3.515825470000 1118356 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": 676645, "vin": [ { "gen": { "height": 676635 } } ], "vout": [ { "amount": 3515825470, "target": { "key": "d6c1a193ba9b34427f28b05fc3de24fa50eebffb602f3c9aa8fc348778daacfa" } } ], "extra": [ 1, 21, 142, 252, 76, 20, 75, 29, 181, 12, 24, 253, 48, 220, 219, 102, 173, 25, 100, 121, 73, 168, 160, 229, 179, 140, 235, 251, 114, 22, 179, 90, 77, 2, 17, 0, 0, 0, 2, 94, 195, 81, 96, 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