Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 410f70a3516f4b545248c3339a741615daf896757b2f7eb9b05b7b9ec72f07ca

Tx prefix hash: d2e8b18fdce70f9964e4af7337f1f3cfd812daa380796f4ffda2ec17720a6d8b
Tx public key: e1ffd1d5f414f640fea3f5f2b48d26f3688074fe8879f4b96cdbdd8375ce4256
Timestamp: 1726576748 Timestamp [UCT]: 2024-09-17 12:39:08 Age [y:d:h:m:s]: 00:234:02:57:17
Block: 1112085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167162 RingCT/type: yes/0
Extra: 01e1ffd1d5f414f640fea3f5f2b48d26f3688074fe8879f4b96cdbdd8375ce4256021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f504795df1bbf8cbff8ad988dc1d3eafda0495ece8e8b9f3da241c2fccd4c8b8 0.600000000000 1591278 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": 1112095, "vin": [ { "gen": { "height": 1112085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f504795df1bbf8cbff8ad988dc1d3eafda0495ece8e8b9f3da241c2fccd4c8b8" } } ], "extra": [ 1, 225, 255, 209, 213, 244, 20, 246, 64, 254, 163, 245, 242, 180, 141, 38, 243, 104, 128, 116, 254, 136, 121, 244, 185, 108, 219, 221, 131, 117, 206, 66, 86, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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