Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 422674f128d8856a95228608334056b4ebd77c4ae1dbfe059e5e8471ae265548

Tx prefix hash: 3dbbcda186c505c498c1b60fb32b3dfc82f32766d521c9d81ad51e570cf5fd02
Tx public key: 10f201efc4b6187a9eddbbdb311354e453296b2338805d19c08aa935a2d824b0
Timestamp: 1710398816 Timestamp [UCT]: 2024-03-14 06:46:56 Age [y:d:h:m:s]: 01:070:21:52:53
Block: 977974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311691 RingCT/type: yes/0
Extra: 0110f201efc4b6187a9eddbbdb311354e453296b2338805d19c08aa935a2d824b0021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a082417e9df0ede47d4d67be1ff6c8cbdf1dc069c52a31d589a002ec9decc9c 0.600000000000 1437983 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": 977984, "vin": [ { "gen": { "height": 977974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a082417e9df0ede47d4d67be1ff6c8cbdf1dc069c52a31d589a002ec9decc9c" } } ], "extra": [ 1, 16, 242, 1, 239, 196, 182, 24, 122, 158, 221, 187, 219, 49, 19, 84, 228, 83, 41, 107, 35, 56, 128, 93, 25, 192, 138, 169, 53, 162, 216, 36, 176, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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