Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aee07aeb3115c216fe360f18763bf798f93bfd432c26009ae0b7133128a261b0

Tx prefix hash: 1b71e997d3f4adfa2fc96dcfbf7ece11f152351f9bd2d8e0c4e3edf78a8fd879
Tx public key: d3441b0fccf59d2251856d59f8f0807a046645a05ecad69ccfff63088c8a4e2c
Timestamp: 1674908901 Timestamp [UCT]: 2023-01-28 12:28:21 Age [y:d:h:m:s]: 02:080:06:38:03
Block: 684604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579003 RingCT/type: yes/0
Extra: 01d3441b0fccf59d2251856d59f8f0807a046645a05ecad69ccfff63088c8a4e2c0211000000025029cbac000000000000000000

1 output(s) for total of 3.308435645000 dcy

stealth address amount amount idx
00: 41f5be5fd3badcde3c189a99d42553d1007126d47901f9ec8c6f6ca7c2ee4ff3 3.308435645000 1126869 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": 684614, "vin": [ { "gen": { "height": 684604 } } ], "vout": [ { "amount": 3308435645, "target": { "key": "41f5be5fd3badcde3c189a99d42553d1007126d47901f9ec8c6f6ca7c2ee4ff3" } } ], "extra": [ 1, 211, 68, 27, 15, 204, 245, 157, 34, 81, 133, 109, 89, 248, 240, 128, 122, 4, 102, 69, 160, 94, 202, 214, 156, 207, 255, 99, 8, 140, 138, 78, 44, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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