Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44012e23783a756d5343ed97764ef3b999b45a41f6ddb23725dad08eec4087a3

Tx prefix hash: 2aa63cc0b4704d666c1bebcd3d02920a8ba29d2fb316fd05e6d1371a0cbe0f19
Tx public key: 35a2d9b5e463ac9f7a608bb19e230c4522d084dffc85d67f5c1efbadcb0582e3
Timestamp: 1695516470 Timestamp [UCT]: 2023-09-24 00:47:50 Age [y:d:h:m:s]: 01:123:10:27:35
Block: 854774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349468 RingCT/type: yes/0
Extra: 0135a2d9b5e463ac9f7a608bb19e230c4522d084dffc85d67f5c1efbadcb0582e302110000000fe6d27f9c000000000000000000

1 output(s) for total of 0.903189654000 dcy

stealth address amount amount idx
00: 903f2f27373543fd2bfc3c12e8e2ba576f0db88b30c596a7782ba050742e1bda 0.903189654000 1308762 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": 854784, "vin": [ { "gen": { "height": 854774 } } ], "vout": [ { "amount": 903189654, "target": { "key": "903f2f27373543fd2bfc3c12e8e2ba576f0db88b30c596a7782ba050742e1bda" } } ], "extra": [ 1, 53, 162, 217, 181, 228, 99, 172, 159, 122, 96, 139, 177, 158, 35, 12, 69, 34, 208, 132, 223, 252, 133, 214, 127, 92, 30, 251, 173, 203, 5, 130, 227, 2, 17, 0, 0, 0, 15, 230, 210, 127, 156, 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