Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98de934d15e917526c1b05a075980d403f98ed15085999c8d1e30fa8dd06f930

Tx prefix hash: 4ba978e687444765d4d5dc4dba3e154a1bee1ea03ebc4e52752b556a1af981cf
Tx public key: 708ff48f49c243104a2f51b0e9aaebf5029a4d510bb6274a211fb967f9a85444
Timestamp: 1729164612 Timestamp [UCT]: 2024-10-17 11:30:12 Age [y:d:h:m:s]: 01:033:19:22:27
Block: 1133537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282529 RingCT/type: yes/0
Extra: 01708ff48f49c243104a2f51b0e9aaebf5029a4d510bb6274a211fb967f9a8544402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94d5f3cfe338aafcf638ca055fdbec5c75485174275d1b2489f071dc9512a3f 0.600000000000 1616664 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": 1133547, "vin": [ { "gen": { "height": 1133537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94d5f3cfe338aafcf638ca055fdbec5c75485174275d1b2489f071dc9512a3f" } } ], "extra": [ 1, 112, 143, 244, 143, 73, 194, 67, 16, 74, 47, 81, 176, 233, 170, 235, 245, 2, 154, 77, 81, 11, 182, 39, 74, 33, 31, 185, 103, 249, 168, 84, 68, 2, 17, 0, 0, 0, 1, 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