Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c030dddcbc46ab46387253a0bb3d06e23321b1e4ce568a53b8c880efd83bdd

Tx prefix hash: 4630f31c399ab9c0aa61cf2a2ed1954d45f0a70f65871e2a9a0008bcf4107483
Tx public key: 4223771c1ae513381f257988d21c4d584b174ce8d1e7125abc421ef6d633d2ae
Timestamp: 1673886135 Timestamp [UCT]: 2023-01-16 16:22:15 Age [y:d:h:m:s]: 02:002:16:49:19
Block: 676107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523824 RingCT/type: yes/0
Extra: 014223771c1ae513381f257988d21c4d584b174ce8d1e7125abc421ef6d633d2ae0211000000018b7b6602000000000000000000

1 output(s) for total of 3.530016960000 dcy

stealth address amount amount idx
00: cfa71ada15839a55ebd03b933c44d7cfcb0be7adae932eb1661dbf8811231a98 3.530016960000 1117816 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": 676117, "vin": [ { "gen": { "height": 676107 } } ], "vout": [ { "amount": 3530016960, "target": { "key": "cfa71ada15839a55ebd03b933c44d7cfcb0be7adae932eb1661dbf8811231a98" } } ], "extra": [ 1, 66, 35, 119, 28, 26, 229, 19, 56, 31, 37, 121, 136, 210, 28, 77, 88, 75, 23, 76, 232, 209, 231, 18, 90, 188, 66, 30, 246, 214, 51, 210, 174, 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