Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a4830507f2852d1df2a19a19163e4168fdc294d1688e3f54bc41f0af1a40f77

Tx prefix hash: 8b93249e983b5234f15e457694622fbb2e1726ec31f88ee30f0f4fd345d07d44
Tx public key: 3725d2626fce7a232c1f13e3a96105f29755280103029fb1c2b73606952be0cb
Timestamp: 1733835891 Timestamp [UCT]: 2024-12-10 13:04:51 Age [y:d:h:m:s]: 00:102:08:28:01
Block: 1172164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72942 RingCT/type: yes/0
Extra: 013725d2626fce7a232c1f13e3a96105f29755280103029fb1c2b73606952be0cb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d1f9495e69aef1708ef80993fc65da5bfd74abf27935b650af3723a9d7c5596 0.600000000000 1658021 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": 1172174, "vin": [ { "gen": { "height": 1172164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d1f9495e69aef1708ef80993fc65da5bfd74abf27935b650af3723a9d7c5596" } } ], "extra": [ 1, 55, 37, 210, 98, 111, 206, 122, 35, 44, 31, 19, 227, 169, 97, 5, 242, 151, 85, 40, 1, 3, 2, 159, 177, 194, 183, 54, 6, 149, 43, 224, 203, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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