Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a3d6b5d5810eab7cb922bc6a843e78bc96af2242b4ccb43d4d1cfa879d56cc1

Tx prefix hash: 50c9ca48f371a9df1c95ea4963df1271582e1ee079b4d4be4071756946de6e7d
Tx public key: 8115c8abc6008447f78d80438e79e5121c24c1371031ba798ee65df504a43709
Timestamp: 1723258720 Timestamp [UCT]: 2024-08-10 02:58:40 Age [y:d:h:m:s]: 00:245:15:44:26
Block: 1084574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175455 RingCT/type: yes/0
Extra: 018115c8abc6008447f78d80438e79e5121c24c1371031ba798ee65df504a4370902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fb32e99516de1d8b6d9d944445a58be8adb919c0fb44946bf9455cac9c723bd 0.600000000000 1558899 of 15

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": 1084584, "vin": [ { "gen": { "height": 1084574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fb32e99516de1d8b6d9d944445a58be8adb919c0fb44946bf9455cac9c723bd" } } ], "extra": [ 1, 129, 21, 200, 171, 198, 0, 132, 71, 247, 141, 128, 67, 142, 121, 229, 18, 28, 36, 193, 55, 16, 49, 186, 121, 142, 230, 93, 245, 4, 164, 55, 9, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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