Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26018ca66a27c49d5eaf1caa64d15c8754e4585d18f638c647a77a78387afa9

Tx prefix hash: c4f2ff8cf2fc887027613f32630463f4361315ae43cc875f80061054f1799df3
Tx public key: 7c41a10a35d3f8e95c2b126481a05a801513bcceaccc14e3f2bbf1fe66f50ae6
Timestamp: 1726443774 Timestamp [UCT]: 2024-09-15 23:42:54 Age [y:d:h:m:s]: 00:278:17:18:59
Block: 1110974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198911 RingCT/type: yes/0
Extra: 017c41a10a35d3f8e95c2b126481a05a801513bcceaccc14e3f2bbf1fe66f50ae602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 627c7cb36a905982e079aef9d6b93cf09e87fe6cced202d2cb2709f1410dc8bf 0.600000000000 1589771 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": 1110984, "vin": [ { "gen": { "height": 1110974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "627c7cb36a905982e079aef9d6b93cf09e87fe6cced202d2cb2709f1410dc8bf" } } ], "extra": [ 1, 124, 65, 161, 10, 53, 211, 248, 233, 92, 43, 18, 100, 129, 160, 90, 128, 21, 19, 188, 206, 172, 204, 20, 227, 242, 187, 241, 254, 102, 245, 10, 230, 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