Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9949bbbbae150039047f7cc9a762e6b8f2f061b7a58241ba497ebb4c7f719d6

Tx prefix hash: bc977f9a45aba904e13e69e884d4b121ff43de4faa6677e10ad5aee555d6cd31
Tx public key: 5381e1bbef3f79d613932a5a4d9abe5328bdc87c83b1fe0a1baf3579aae7aaa9
Timestamp: 1729697782 Timestamp [UCT]: 2024-10-23 15:36:22 Age [y:d:h:m:s]: 00:070:00:32:49
Block: 1137930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50051 RingCT/type: yes/0
Extra: 015381e1bbef3f79d613932a5a4d9abe5328bdc87c83b1fe0a1baf3579aae7aaa9021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cb161074629a71ac25f24a7390959020e3b555f44c6a1251a1d4fa7a5de8312 0.600000000000 1621517 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": 1137940, "vin": [ { "gen": { "height": 1137930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cb161074629a71ac25f24a7390959020e3b555f44c6a1251a1d4fa7a5de8312" } } ], "extra": [ 1, 83, 129, 225, 187, 239, 63, 121, 214, 19, 147, 42, 90, 77, 154, 190, 83, 40, 189, 200, 124, 131, 177, 254, 10, 27, 175, 53, 121, 170, 231, 170, 169, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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