Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0db2a3073e7ace2bee851b830490c91b91cf7f15ed48c6932f12402c80dc110

Tx prefix hash: cc764977f59464987206c6fb1c5a6cabb1e012c80e126786d771bbfda3311d1c
Tx public key: d1d7a3e15ca3e75c83a0f174a1c85cfa6985813e3954cc6d1225cc2fd50964ee
Timestamp: 1705142490 Timestamp [UCT]: 2024-01-13 10:41:30 Age [y:d:h:m:s]: 01:131:06:06:07
Block: 934362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354950 RingCT/type: yes/0
Extra: 01d1d7a3e15ca3e75c83a0f174a1c85cfa6985813e3954cc6d1225cc2fd50964ee0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c9123e8fc7197cc15b85d794ede7779be2a98f17552e2a5839195bcb1b773c2 0.600000000000 1392368 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": 934372, "vin": [ { "gen": { "height": 934362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c9123e8fc7197cc15b85d794ede7779be2a98f17552e2a5839195bcb1b773c2" } } ], "extra": [ 1, 209, 215, 163, 225, 92, 163, 231, 92, 131, 160, 241, 116, 161, 200, 92, 250, 105, 133, 129, 62, 57, 84, 204, 109, 18, 37, 204, 47, 213, 9, 100, 238, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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