Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e650562fc307ec55ff3bf435264f8ee6d19de0625e366ce2049e78bd54bba3e

Tx prefix hash: d544a74df6f6c23d80b856eaab47b381d6acdbbcd2d93b209a346eb191506268
Tx public key: f368e88e2d1b8933c37dd4cb6a81c9c30754f382aaa536e57a3c6e455901b892
Timestamp: 1725526067 Timestamp [UCT]: 2024-09-05 08:47:47 Age [y:d:h:m:s]: 00:224:22:32:21
Block: 1103371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160616 RingCT/type: yes/0
Extra: 01f368e88e2d1b8933c37dd4cb6a81c9c30754f382aaa536e57a3c6e455901b892021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b247db44796156264000a766c1bd039f681ca2da3e089fe76f6c0851a32eb217 0.600000000000 1580174 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": 1103381, "vin": [ { "gen": { "height": 1103371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b247db44796156264000a766c1bd039f681ca2da3e089fe76f6c0851a32eb217" } } ], "extra": [ 1, 243, 104, 232, 142, 45, 27, 137, 51, 195, 125, 212, 203, 106, 129, 201, 195, 7, 84, 243, 130, 170, 165, 54, 229, 122, 60, 110, 69, 89, 1, 184, 146, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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