Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c13ac226fd720ac178dc7070918b988be8262776e3d8f2da1da4f6d6a3620b

Tx prefix hash: 0f009550f06c43fda0e1ff59e77901a54f9cef663e5f1cf03f5be573e5eba5c8
Tx public key: 3aa3f585549390dcd4e34091ac1a0794e3e5f18047a27dcc4438c882eb4f9c58
Timestamp: 1700996458 Timestamp [UCT]: 2023-11-26 11:00:58 Age [y:d:h:m:s]: 01:053:18:57:40
Block: 900000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299836 RingCT/type: yes/0
Extra: 013aa3f585549390dcd4e34091ac1a0794e3e5f18047a27dcc4438c882eb4f9c5802110000000133af99f4000000000000000000

1 output(s) for total of 0.639636393000 dcy

stealth address amount amount idx
00: 0bc5867bed3aac3be7d2789cd51bf30da828c7725c1efb2db922119f7141a366 0.639636393000 1356473 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": 900010, "vin": [ { "gen": { "height": 900000 } } ], "vout": [ { "amount": 639636393, "target": { "key": "0bc5867bed3aac3be7d2789cd51bf30da828c7725c1efb2db922119f7141a366" } } ], "extra": [ 1, 58, 163, 245, 133, 84, 147, 144, 220, 212, 227, 64, 145, 172, 26, 7, 148, 227, 229, 241, 128, 71, 162, 125, 204, 68, 56, 200, 130, 235, 79, 156, 88, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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