Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a8380a20405e37adb447fdde2dc2d1940c43bada29a6c7380b5719aa6656f8e

Tx prefix hash: b7858218c8b0078d9c8e6af0ccebaf40615545707e141c880255dc50b494e7e4
Tx public key: f6cea65bf62a9fc3a76c9c9080cb6a1e20c4e79593a0c4a37a897119bac6d999
Timestamp: 1709963879 Timestamp [UCT]: 2024-03-09 05:57:59 Age [y:d:h:m:s]: 01:100:18:59:57
Block: 974359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332945 RingCT/type: yes/0
Extra: 01f6cea65bf62a9fc3a76c9c9080cb6a1e20c4e79593a0c4a37a897119bac6d99902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5380bdb418865e73a8f5716feaacf209a35619e4bd80ba4aa9332f30179c902 0.600000000000 1434314 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": 974369, "vin": [ { "gen": { "height": 974359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5380bdb418865e73a8f5716feaacf209a35619e4bd80ba4aa9332f30179c902" } } ], "extra": [ 1, 246, 206, 166, 91, 246, 42, 159, 195, 167, 108, 156, 144, 128, 203, 106, 30, 32, 196, 231, 149, 147, 160, 196, 163, 122, 137, 113, 25, 186, 198, 217, 153, 2, 17, 0, 0, 0, 1, 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