Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7058283abc65ce14a6d4e1852784bdfe73c60ba5bddc2f7a51d7a5e428014984

Tx prefix hash: 9562f8aabf769e3904787bbf643a0202c0f0e670d10ba74fcfedc0a1bac77a8c
Tx public key: 58e554293428c5f12e1779c6837fb49aa11fbf5784778b3c745b3cb804568eaa
Timestamp: 1716885171 Timestamp [UCT]: 2024-05-28 08:32:51 Age [y:d:h:m:s]: 00:353:06:01:17
Block: 1031743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252486 RingCT/type: yes/0
Extra: 0158e554293428c5f12e1779c6837fb49aa11fbf5784778b3c745b3cb804568eaa0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a1f1dfa4250358e6f236bd8f76a8c167e5b358a990b968c15537fc9d697fc72 0.600000000000 1500192 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": 1031753, "vin": [ { "gen": { "height": 1031743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a1f1dfa4250358e6f236bd8f76a8c167e5b358a990b968c15537fc9d697fc72" } } ], "extra": [ 1, 88, 229, 84, 41, 52, 40, 197, 241, 46, 23, 121, 198, 131, 127, 180, 154, 161, 31, 191, 87, 132, 119, 139, 60, 116, 91, 60, 184, 4, 86, 142, 170, 2, 17, 0, 0, 0, 2, 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