Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d20dbd9bd81e7265fae163dc58d6aa7b455fb9e5127d1009ac921ae43fccc6c

Tx prefix hash: 71bccc7c05ed189dc9865b19cd7b55fd88272ddce183e38303826c07acfddef1
Tx public key: 1d6a949b719fead9df85c8a3e56ee29eb3f2091e618fe8a0bd9ac24d5be1e35c
Timestamp: 1718199354 Timestamp [UCT]: 2024-06-12 13:35:54 Age [y:d:h:m:s]: 00:276:01:17:00
Block: 1042639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197276 RingCT/type: yes/0
Extra: 011d6a949b719fead9df85c8a3e56ee29eb3f2091e618fe8a0bd9ac24d5be1e35c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4bf3e43652ccfb4e2277e36747e7e405978ce699d0ab723fb19f9e8e1bb379 0.600000000000 1511602 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": 1042649, "vin": [ { "gen": { "height": 1042639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4bf3e43652ccfb4e2277e36747e7e405978ce699d0ab723fb19f9e8e1bb379" } } ], "extra": [ 1, 29, 106, 148, 155, 113, 159, 234, 217, 223, 133, 200, 163, 229, 110, 226, 158, 179, 242, 9, 30, 97, 143, 232, 160, 189, 154, 194, 77, 91, 225, 227, 92, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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