Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b18c1fe78a6bb87b8e72d03c96e435d3b2cd99f41b934e56fd60574044dbc216

Tx prefix hash: deee95b92616c99509d5672f5babee687dcd014c3d8dba3f1832f6f8145ebde0
Tx public key: 3dc44aae8338cdfeeb2c1e406e61e175796c2219ff4d0a4425716b5b160403fc
Timestamp: 1676322479 Timestamp [UCT]: 2023-02-13 21:07:59 Age [y:d:h:m:s]: 02:071:12:46:08
Block: 696340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572730 RingCT/type: yes/0
Extra: 013dc44aae8338cdfeeb2c1e406e61e175796c2219ff4d0a4425716b5b160403fc0211000000015029cbac000000000000000000

1 output(s) for total of 3.025077004000 dcy

stealth address amount amount idx
00: c0255e60b81659d58a662724d5db5579efdcfc9f16b80628bfd2190d7fd8ebe2 3.025077004000 1139327 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": 696350, "vin": [ { "gen": { "height": 696340 } } ], "vout": [ { "amount": 3025077004, "target": { "key": "c0255e60b81659d58a662724d5db5579efdcfc9f16b80628bfd2190d7fd8ebe2" } } ], "extra": [ 1, 61, 196, 74, 174, 131, 56, 205, 254, 235, 44, 30, 64, 110, 97, 225, 117, 121, 108, 34, 25, 255, 77, 10, 68, 37, 113, 107, 91, 22, 4, 3, 252, 2, 17, 0, 0, 0, 1, 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