Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0313e04a2cd7fcd44bd57121b3679f0461da08c9639250f49e8d1d468c7d6caa

Tx prefix hash: d194632b7cb9c1d07a15c1a4b1e57ac59aa603d31014e1ff99259cf0d3a7975a
Tx public key: 6a38212a9d5d0937f9301753f63cd92147623ef1748d668e5a35d83e45e46f56
Timestamp: 1739674956 Timestamp [UCT]: 2025-02-16 03:02:36 Age [y:d:h:m:s]: 00:278:21:19:24
Block: 1220200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197105 RingCT/type: yes/0
Extra: 016a38212a9d5d0937f9301753f63cd92147623ef1748d668e5a35d83e45e46f56021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f48efde5827cdab0c1c979dea8ab76317bfd8c01ecfa6208b386a2b981c5750e 0.600000000000 1707037 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": 1220210, "vin": [ { "gen": { "height": 1220200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f48efde5827cdab0c1c979dea8ab76317bfd8c01ecfa6208b386a2b981c5750e" } } ], "extra": [ 1, 106, 56, 33, 42, 157, 93, 9, 55, 249, 48, 23, 83, 246, 60, 217, 33, 71, 98, 62, 241, 116, 141, 102, 142, 90, 53, 216, 62, 69, 228, 111, 86, 2, 17, 0, 0, 0, 3, 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