Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f450f7612eee4b713d4f008ba0df52d315210d96970137696dda9e7ddf273cf6

Tx prefix hash: e5ebc7b082533b2a50cfa624aaff1c5883e31ad8a862a282422dfcfad5cc569f
Tx public key: 92a6f81c38f572ca0c517cc077b8efeb4e3d4abab8e6c35521d290c471dfc974
Timestamp: 1727411870 Timestamp [UCT]: 2024-09-27 04:37:50 Age [y:d:h:m:s]: 00:234:16:59:56
Block: 1119009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167578 RingCT/type: yes/0
Extra: 0192a6f81c38f572ca0c517cc077b8efeb4e3d4abab8e6c35521d290c471dfc97402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fcad3bf593426e17aa849c253cc1d2644d601e1677f86debcbbdb6c8bc0c8d7 0.600000000000 1600402 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": 1119019, "vin": [ { "gen": { "height": 1119009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fcad3bf593426e17aa849c253cc1d2644d601e1677f86debcbbdb6c8bc0c8d7" } } ], "extra": [ 1, 146, 166, 248, 28, 56, 245, 114, 202, 12, 81, 124, 192, 119, 184, 239, 235, 78, 61, 74, 186, 184, 230, 195, 85, 33, 210, 144, 196, 113, 223, 201, 116, 2, 17, 0, 0, 0, 3, 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