Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341835f8d837ee921b4cd91a288060848921ce0d8da35957724b08beaacca12e

Tx prefix hash: 3873ca3b212c4e3a3fc5bea62de99d6ed8ce8040f7cee6eea9d38525a698b6d2
Tx public key: 03fdc4834c41e84940abb1d32119789c50d9b73f241bae76b8616718e8ce14b6
Timestamp: 1648657779 Timestamp [UCT]: 2022-03-30 16:29:39 Age [y:d:h:m:s]: 02:274:02:25:29
Block: 469684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715510 RingCT/type: yes/0
Extra: 0103fdc4834c41e84940abb1d32119789c50d9b73f241bae76b8616718e8ce14b602110000000306faf294000000000000000000

1 output(s) for total of 17.050698806000 dcy

stealth address amount amount idx
00: 7ca1a391efe276a413e45df312f4130e37242d4b753110a636cd9d18ecb7d9f1 17.050698806000 888676 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": 469694, "vin": [ { "gen": { "height": 469684 } } ], "vout": [ { "amount": 17050698806, "target": { "key": "7ca1a391efe276a413e45df312f4130e37242d4b753110a636cd9d18ecb7d9f1" } } ], "extra": [ 1, 3, 253, 196, 131, 76, 65, 232, 73, 64, 171, 177, 211, 33, 25, 120, 156, 80, 217, 183, 63, 36, 27, 174, 118, 184, 97, 103, 24, 232, 206, 20, 182, 2, 17, 0, 0, 0, 3, 6, 250, 242, 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