Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f12c63fb7bef1e71619fc13fbf57f629964fe04d972630eb5f7ec003fb8612f

Tx prefix hash: ba443cde6911869b9308473b116822d0cb89d9843121c6840c1a4ad1d5897b3c
Tx public key: 76d49a3946bef5bd839ac28c90802d3af6b881fd6f9500494dee8d2c3cf0ee91
Timestamp: 1704507539 Timestamp [UCT]: 2024-01-06 02:18:59 Age [y:d:h:m:s]: 01:309:01:53:14
Block: 929087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479747 RingCT/type: yes/0
Extra: 0176d49a3946bef5bd839ac28c90802d3af6b881fd6f9500494dee8d2c3cf0ee910211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0d27802a4fe06d44ec83457a5e1a0114d2605ca8388dab97680febc41d27f28 0.600000000000 1386955 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": 929097, "vin": [ { "gen": { "height": 929087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0d27802a4fe06d44ec83457a5e1a0114d2605ca8388dab97680febc41d27f28" } } ], "extra": [ 1, 118, 212, 154, 57, 70, 190, 245, 189, 131, 154, 194, 140, 144, 128, 45, 58, 246, 184, 129, 253, 111, 149, 0, 73, 77, 238, 141, 44, 60, 240, 238, 145, 2, 17, 0, 0, 0, 4, 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