Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a6fc1f80211e651036dd0575e7221101b3e97f1dc99954371b2bf3c960f1cd4

Tx prefix hash: e3fb1bd316fb0a3b56615b10fef15fb940ec47c94f09fd4abb00556e759e952f
Tx public key: 0feee96a09865b69d4e6b74ac328a2ebd4eef3843023650c5842aff209e7343a
Timestamp: 1706848185 Timestamp [UCT]: 2024-02-02 04:29:45 Age [y:d:h:m:s]: 01:136:14:52:44
Block: 948511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358639 RingCT/type: yes/0
Extra: 010feee96a09865b69d4e6b74ac328a2ebd4eef3843023650c5842aff209e7343a02110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032b13faa25820d08878ddbd077c504bb9df9a717477ff38d9c79ae9ae1df19b 0.600000000000 1406931 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": 948521, "vin": [ { "gen": { "height": 948511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032b13faa25820d08878ddbd077c504bb9df9a717477ff38d9c79ae9ae1df19b" } } ], "extra": [ 1, 15, 238, 233, 106, 9, 134, 91, 105, 212, 230, 183, 74, 195, 40, 162, 235, 212, 238, 243, 132, 48, 35, 101, 12, 88, 66, 175, 242, 9, 231, 52, 58, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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