Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033254fbc359d43cef5a7b330bf2f3bb2268a46c5131e9bff0412408fee78cca

Tx prefix hash: d3238a72801137e1c0e34a8780b15c6417ba5029d4c99544841a40ff5f7e8324
Tx public key: 0b7da30c2c902055a50b4a02bfc5a602ef79c8c5441dda2c2ff069cf42b524c1
Timestamp: 1724838292 Timestamp [UCT]: 2024-08-28 09:44:52 Age [y:d:h:m:s]: 00:179:00:50:41
Block: 1097662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127780 RingCT/type: yes/0
Extra: 010b7da30c2c902055a50b4a02bfc5a602ef79c8c5441dda2c2ff069cf42b524c1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1579ad16af00b1bbbac45f9c001d8c8c3be4e2ece0a68a87b9acebf308173622 0.600000000000 1573107 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": 1097672, "vin": [ { "gen": { "height": 1097662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1579ad16af00b1bbbac45f9c001d8c8c3be4e2ece0a68a87b9acebf308173622" } } ], "extra": [ 1, 11, 125, 163, 12, 44, 144, 32, 85, 165, 11, 74, 2, 191, 197, 166, 2, 239, 121, 200, 197, 68, 29, 218, 44, 47, 240, 105, 207, 66, 181, 36, 193, 2, 17, 0, 0, 0, 2, 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