Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588bdcc74432479c0908a9c82b151f36855510f1145d74b27ec06fd6ccc84ffc

Tx prefix hash: 44fb2bf916f253ee0824404f17c22bd14227ab5108dee48d5ad2cf42d94b92bd
Tx public key: 321bf24971616f4f91cf98f3909b946bc676b9c50fbb0d5f7bb733bc4241b9ce
Timestamp: 1717508968 Timestamp [UCT]: 2024-06-04 13:49:28 Age [y:d:h:m:s]: 00:284:09:31:48
Block: 1036914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203260 RingCT/type: yes/0
Extra: 01321bf24971616f4f91cf98f3909b946bc676b9c50fbb0d5f7bb733bc4241b9ce0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f88c1d5827fb40a52ca5a6643b8fc9f3c9f1029464aa1bdf8905af068a2f3d2 0.600000000000 1505445 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": 1036924, "vin": [ { "gen": { "height": 1036914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f88c1d5827fb40a52ca5a6643b8fc9f3c9f1029464aa1bdf8905af068a2f3d2" } } ], "extra": [ 1, 50, 27, 242, 73, 113, 97, 111, 79, 145, 207, 152, 243, 144, 155, 148, 107, 198, 118, 185, 197, 15, 187, 13, 95, 123, 183, 51, 188, 66, 65, 185, 206, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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