Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb183707570dada5e9c33235b69ada28cccfcff264f085b6ce1d870efaa2b61e

Tx prefix hash: b646c4f8f4625a609bae7ef33ebc5031265621c7a0b2c02e2ab37ff77eef20bf
Tx public key: dd4153fb8734bbd53137e324d508fa81dc644bfdd28ba1cab9e7922cf961fcd1
Timestamp: 1697456357 Timestamp [UCT]: 2023-10-16 11:39:17 Age [y:d:h:m:s]: 01:225:16:42:47
Block: 870858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422380 RingCT/type: yes/0
Extra: 01dd4153fb8734bbd53137e324d508fa81dc644bfdd28ba1cab9e7922cf961fcd1021100000003faf35c9c000000000000000000

1 output(s) for total of 0.798888118000 dcy

stealth address amount amount idx
00: aa9b7657ac968b6552429b5497b7942b0b9c1ddb3abec56b11f054b828dd6df6 0.798888118000 1325813 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": 870868, "vin": [ { "gen": { "height": 870858 } } ], "vout": [ { "amount": 798888118, "target": { "key": "aa9b7657ac968b6552429b5497b7942b0b9c1ddb3abec56b11f054b828dd6df6" } } ], "extra": [ 1, 221, 65, 83, 251, 135, 52, 187, 213, 49, 55, 227, 36, 213, 8, 250, 129, 220, 100, 75, 253, 210, 139, 161, 202, 185, 231, 146, 44, 249, 97, 252, 209, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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