Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1392a32123e718d845fdeaa5520da1a5d75d486bd5608d6b1acc6d1caeaa1420

Tx prefix hash: 2e8769552fd439580562e62b45d1e872a990c6b181b2f039261ad8151eab4347
Tx public key: b42417f1c294109e7a6d86eb8c364ad08299f05a11ab7f93adb400af8fd204b7
Timestamp: 1711903250 Timestamp [UCT]: 2024-03-31 16:40:50 Age [y:d:h:m:s]: 01:041:13:20:35
Block: 990442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290667 RingCT/type: yes/0
Extra: 01b42417f1c294109e7a6d86eb8c364ad08299f05a11ab7f93adb400af8fd204b70211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18289ed481cfb7ae6d44489ba510e0d13b94ce06c432fdf7bf4594583fdad36 0.600000000000 1450764 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": 990452, "vin": [ { "gen": { "height": 990442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18289ed481cfb7ae6d44489ba510e0d13b94ce06c432fdf7bf4594583fdad36" } } ], "extra": [ 1, 180, 36, 23, 241, 194, 148, 16, 158, 122, 109, 134, 235, 140, 54, 74, 208, 130, 153, 240, 90, 17, 171, 127, 147, 173, 180, 0, 175, 143, 210, 4, 183, 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