Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3a72a0174ea6e54895fe9caaeba5765272b1ff1fcd026ca74db5d83f22ce808

Tx prefix hash: e011594d545503e42c0722cb59c47635be3ad6c05468bdc9dec412aa2e5935c6
Tx public key: 977bdf20187a0878c1a5757f9dbc6b88334704e1e4e0a2da5d5fe80ce224a667
Timestamp: 1716413712 Timestamp [UCT]: 2024-05-22 21:35:12 Age [y:d:h:m:s]: 00:245:04:54:45
Block: 1027824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175442 RingCT/type: yes/0
Extra: 01977bdf20187a0878c1a5757f9dbc6b88334704e1e4e0a2da5d5fe80ce224a66702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f52626271128c2db308deaa882f93aab69bebb011c2f0a2b9a741577a7add741 0.600000000000 1495653 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": 1027834, "vin": [ { "gen": { "height": 1027824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f52626271128c2db308deaa882f93aab69bebb011c2f0a2b9a741577a7add741" } } ], "extra": [ 1, 151, 123, 223, 32, 24, 122, 8, 120, 193, 165, 117, 127, 157, 188, 107, 136, 51, 71, 4, 225, 228, 224, 162, 218, 93, 95, 232, 12, 226, 36, 166, 103, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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